Storage containers, systems and methods

ABSTRACT

A system embodiment includes a container base having an identifier of one container type encoded according to one scheme and a container lid including the identifier of the container type encoded according to the scheme. A method implementation of assembling containers includes selecting a container base from a plurality of container bases and establishing a type of the container base by recognizing an identifier encoded on the base according to a scheme. Then, selecting from a plurality of container lids, a container lid having an encoded identifier matching the identifier on the container base and engaging the selected container lid with the selected container base. An app implementation accepts a choice of container category, receives input of an identifier for the container, accepts input of contents and location of the container, generates a current date or receives an input date, associates and stores the category, identifier, contents, date and location.

REFERENCE TO PENDING PRIOR PATENT APPLICATION

This application claims the benefit under 35 U.S.C. 119 (e) of U.S. Provisional Patent Application No. 61/812,626, filed Apr. 16, 2013 by Daniel Kouri for “Storage Containers” which patent application is hereby incorporated herein by reference.

BACKGROUND

Generally, for centuries people have used containers to store and organize possessions. Some containers are provided as a simple receptacle without a closure whereas other containers are provided with one of a variety of types of lid. Some containers are provided with coupled or integral lids while others include lids that are partially or completely separable therefrom. When lids not permanently coupled with the container base, they are frequently separated from the base and it may become difficult to choose, from among a number of containers and lids of different sizes or shapes, matching lids and containers and/or to differentiate contents of closed containers.

SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key aspects or essential aspects of the claimed subject matter. Moreover, this Summary is not intended for use as an aid in determining the scope of the claimed subject matter.

In an embodiment, there is provided a system for assembling containers includes a first container base including an identifier of a first container type encoded according to a first scheme and a first container lid including the identifier of the first container type encoded according to the first scheme.

An embodiment of method of assembling containers includes selecting a first container base from among a plurality of container bases and establishing a type of the first container base by recognizing an identifier encoded on the base according to a first scheme. After establishing the type of the first container base a user selects, from among a plurality of container lids, a first container lid having an encoded identifier matching the identifier on the container base and engages the first container lid with the first container base.

In various implementations, a computer implemented method for a user device may accept a user choice of a category of container. The category of container may be selected by the user from a list including food, storage, content, and/or the like. The computer implemented method may receive user input of an identifier for the container. The computer implemented method may also accept user input of contents and location of the container and generate a current date or receive a date input from the user. The category, identifier, input contents, location, and generated or input date may be associated and stored. The category, identifier, input contents, location and generated or input date may be stored to the user device, a general purpose processor based device associated with the user device, a remote storage site, a computing cloud, local server, and/or the like.

In various different implementations the computer-implemented method may offer the user a selection to “take a picture” of the contents of the container, and may store the picture with the category, identifier, input contents, location and generated or input date. This selection to take a picture may capture a photograph of the contents using the user's device. Alternatively, the picture may be a stock photo of contents of the type input by the user.

In a variety of implementations, the computer implemented method may offer the user an interface to set at least one alert to remind the user of contents of the container. This alert may be is in the form of a calendar reminder, a text, an email, SMS, MMS, and/or the like and the computer implemented method may offer the user an option in this interface to send the alert(s) to a third party in the same or different form. This third party may be selected from a contact list in the user's device.

The computer implemented method may also offer the user an option to randomly generate a recipe for food in the container from a list of recipes, in accordance with various implementations. In some implementations, the user may select this option by shaking the user device. The list of recipes may be a list of the user's recipes, and the computer implemented method may provide the user an interface to post recipes to a social website, or the like.

The computer implemented method may provide the user a search bar to receive at least part of at least one keyword input by the user. Whereupon, stored input contents, categories, identifiers, and/or dates may be searched for the keyword(s) and the results displayed for the user.

Some computer implemented method embodiments may allow the user to input the same identifier for at least one other container, accept user input of contents of the other container, generate a current date or receive a date input by the user, accept an input location of the container, and associate and store the input contents, location and date associated with the other container(s) with the category, identifier, input contents, location, and date of the original container.

Other embodiments are also disclosed. Additional objects, advantages and novel features of the technology will be set forth in part in the description which follows, and in part will become more apparent to those skilled in the art upon examination of the following, or may be learned from practice of the technology.

BRIEF DESCRIPTION OF THE FIGURES

Non-limiting and non-exhaustive embodiments of the present invention, including the preferred embodiment, are described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various views unless otherwise specified. Illustrative embodiments of the invention are illustrated in the drawings, in which:

FIG. 1 illustrates a storage container of a first type in a closed configuration including a container type identifier encoded, according to one embodiment.

FIG. 2 illustrates the storage container of FIG. 1 in an open configuration with the lid separated from base, according to one embodiment.

FIG. 3 illustrates a storage container of a second type in a closed configuration including a container type identifier encoded, according to the embodiments of FIGS. 1 and 2.

FIG. 4 illustrates the storage container of FIG. 3 in an open configuration with lid separated from base, according to one embodiment.

FIG. 5 illustrates a storage container of a third type in a closed configuration including a container type identifier encoded, according to one embodiment.

FIG. 6 illustrates the storage container of FIG. 5 in an open configuration with lid separated from base, according to one embodiment.

FIG. 7 illustrates a storage container of a fourth type in a closed configuration including a container type identifier encoded, according to one embodiment.

FIG. 8 illustrates the storage container of FIG. 7 in an open configuration with lid separated from base, according to one embodiment.

FIG. 9 illustrates a storage container of the first type in a closed configuration and including container type identifiers encoded, including the color red, according to one embodiment.

FIG. 10 illustrates a storage container of the second type in a closed configuration and including container type identifiers encoded, including the color blue, according to one embodiment.

FIG. 11 illustrates a storage container of the third type in a closed configuration and including container type identifiers encoded, including the color green, according to one embodiment.

FIG. 12 illustrates a storage container of the fourth type in a closed configuration and including container type identifiers encoded, including the color yellow, according to one embodiment.

FIG. 13 illustrates a storage container of the second type in a closed configuration including container type identifiers encoded, including a palpable identifier, according to one embodiment.

FIG. 14 illustrates a storage container of a fifth type in a closed configuration including container type identifiers encoded, according to one embodiment.

FIG. 15 illustrates a storage container of the fifth type in an open configuration including container type identifiers encoded, according to one embodiment.

FIG. 16 illustrates a storage container with a matching shape identifier and palpable encoding, according to one embodiment.

FIG. 17 illustrates another storage container with matching shape identifiers and palpable encoding, according to one embodiment.

FIG. 18 illustrates a flow diagram of an example method for assembling storage containers, according to one embodiment.

FIG. 19 illustrates a flow diagram of an example computer implemented storage container inventory method, according to one embodiment.

DETAILED DESCRIPTION

Embodiments are described more fully below in sufficient detail to enable those skilled in the art to practice the system and method. However, embodiments may be implemented in many different forms and should not be construed as being limited to the embodiments set forth herein. The following detailed description is, therefore, not to be taken in a limiting sense.

In an embodiment, a system for assembling containers overcomes the difficulties associated with finding container bases and container lids that match and thereby eliminates the necessity for repeatedly trying selected lids on a container until the appropriate lid is confirmed.

The system for assembling containers includes one container configured in a first size (volume, perimeter dimensions, etc.) and shape, and may further include one or more containers configured in one or a plurality of other sizes and shapes. All container bases having a given size and shape as well as all lids configured to fit these container bases are considered to be of a particular type. Thus, lids and bases of a particular type may be encoded according to one or more schemes or protocols such that their correspondence is more apparent.

With reference to FIGS. 1 and 2, a container 100, including a container base 110 and a container lid 160 is formed of a shape and size (volume, perimeter dimensions, etc.) defining it as being of a first type. Container bases 110 include an identifier for a first container type encoded according to various embodiments making use of one or more numbers 115, such as, by way of example, embossed into bottom 111 of base 110, as illustrated. However, the identifier may, additionally or alternatively, be defined in sidewall 112 of base 110, in accordance with various alternative embodiments. Container lids 160 also include the identifier for the first container type encoded according to such embodiments, making use of one or more numbers 165, such as, by way of example, embossed into top 161 of lid 160, as illustrated. While the identifiers shown in FIGS. 1 through 13 are numbers, any sufficiently differentiable and readily identifiable designation may be used, such as, by way of example one or more of any identical number(s), letter(s), picture(s), drawing(s), symbol(s), etc. In some embodiments, braille, or the like, corresponding to the identifier, or otherwise, may also, or alternatively, be disposed on the lid and container, as discussed below. Examples of non-alphanumeric identifiers may include, shapes, pictures, logos of college National Football League, National Hockey League, National Basketball Association, Major League Baseball, National Association for Stock Car Auto Racing (NASCAR), or similar teams, images of athletes or celebrities, cartoon characters, or the like. Returning to FIG. 2, in various embodiments, the one or more numbers 115 match the one or more numbers 165 to facilitate pairing of container base 110 with an appropriate container lid 160.

With reference to FIGS. 3 and 4, a container 200, including a container base 210 and a container lid 260 is formed of a shape and size (volume, perimeter dimensions, etc.) defining it as being of a second type. Container bases 210 include an identifier for a second container type encoded according to such embodiments making use of one or more numbers 215, such as, by way of example, embossed into bottom 211 of base 210, as illustrated. However, the identifier may, additionally or alternatively, be defined in sidewall 212 of base 210, in accordance with various alternative embodiments. Container lids 260 also include an identifier for the second container type encoded according to such embodiments making use of one or more numbers 265, such as by way of example, embossed into top 261 of lid 260, as illustrated. . In such embodiments, the one or more numbers 215 match the one or more numbers 265 to facilitate pairing of container base 210 with an appropriate container lid 260.

With reference to FIGS. 5 and 6, a container 300, including a container base 310 and a container lid 360 is formed of a shape and size (volume, perimeter dimensions, etc.) defining it as being of a third type. Container bases 310 include an identifier for the third container type encoded according to such embodiments making use of one or more numbers 315, such as, by way of example, embossed into bottom 311 of base 310, as illustrated. However, the identifier may, additionally or alternatively, be defined in sidewall 312 of base 110, in accordance with various alternative embodiments. Container lids 360 also include an identifier for the third container type, encoded according to such embodiments making use of one or more numbers 365, such as by way of example, embossed into top 361 of lid 360, as illustrated. In such embodiments, the one or more numbers 315 match the one or more numbers 365 to facilitate pairing of container base 310 with an appropriate container lid 360.

With reference to FIGS. 7 and 8, a container 400, including a container base 410 and a container lid 460 is formed of a shape and size (volume, perimeter dimensions, etc.) defining it as being of a fourth type. Container bases 410 include an identifier for a fourth container type encoded according to such embodiments making use of one or more numbers 415, such as, by way of example, embossed into bottom 411 of base 410, as illustrated. However, the identifier may, additionally or alternatively, may be defined in sidewall 412 of base 410, in accordance with various alternative embodiments. Container lids 460 also include an identifier for a fourth container type encoded according to such embodiments making use of one or more numbers 465, such as by way of example, embossed into top 461 of lid 460, as illustrated. In such embodiments, the one or more numbers 415 match the one or more numbers 465 to facilitate pairing of container base 410 with an appropriate container lid 460.

With reference to FIGS. 9 through 12, container 500 includes identifiers for a first container type, container 600 includes identifiers for a second container type, container 700 includes identifiers for a third container type and container 800 includes identifiers for a fourth container type, in accordance with FIGS. 1 through 8 discussed above. As illustrated by way of example, the identifiers included on containers 500, 600, 700 and 800 are encoded according to various embodiments making use of colors in addition to various embodiments making use of numbers. For example, each of containers 500, 600, 700 and 800 are each provided in a different color, for example red, blue, green and yellow, respectively. In such embodiments, the color of container lids of 560, 660, 760 and 860 match with the color of container bases 510, 610, 710 and 810. Additionally in some embodiments, such as illustrated, the identifiers (illustrated as numbers) 565, 665, 765 and 865 included on lids 560, 660, 760 and 860, respectively match identifiers (numbers) included on the bottom interior surface of bases 510, 610, 710 and 810, respectively, consistent with the embodiments illustrated in, and described with respect to, FIGS. 1 through 8, above.

With reference to FIG. 13, a container 900, including a container base 910 and a container lid 660 is formed of a shape and size (volume, perimeter dimensions, etc.) defining it as being of the second type discussed above. Container bases 910, in addition to including an identifier for the second container type encoded according to such embodiments making use of one or more numbers 915, also include an identifier for the second container type encoded according to various embodiments making use of Braille or other palpable indicia 916. In the illustrated example, identifier number 915 and palpable indicia 916 are embossed into bottom 911 of base 910. However, the identifier and/or palpable indicia may, additionally or alternatively, be defined in sidewall 912 of base 910, in accordance with various alternative embodiments.

Again referring to FIG. 13, in addition to including an identifier for the second container type encoded according to such embodiments making use of one or more numbers 965, container lids 960 also include an identifier for the second container type encoded according to such embodiments making use of Braille or other palpable indicia 966, such as by way of example, embossed into top 961 of lid 960, as illustrated. In such embodiments, palpable indicia 916 matches palpable indicia 966 to facilitate pairing of container base 910 with an appropriate container lid 960.

With reference to FIGS. 14 and 15, a container 1000, including a container base 1010 and a container lid 1060 is formed of a shape (in the illustrated example, round) and size (volume, perimeter dimensions, etc.) defining it as being of a fifth type. Container bases 1010, in addition to including an identifier for a fourth container type encoded according to such embodiments making use of one or more letters 1015, also include an identifier for the fourth container type encoded according to such embodiments making use of Braille or other palpable indicia 1016. In the illustrated example, identifier letter 1015 and palpable indicia 1016 are embossed into bottom 1011 of base 1010. However, the identifier and/or palpable indicia may, additionally or alternatively, be defined in sidewall 1012 of base 1010, in accordance with various alternative embodiments.

Again referring to FIGS. 14 and 15, in addition to including an identifier for a fifth container type encoded according to such embodiments making use of one or more letters 1065, container lids 1060 also include an identifier for the fourth container type encoded according to such embodiments making use of Braille or other palpable indicia 1066, such as by way of example, embossed into top 1061 of lid 1060, as illustrated. In such embodiments, palpable indicia 1016 matches the palpable indicia 1066 to facilitate pairing of container base 1010 with an appropriate container lid 1060.

FIGS. 16 and 17 illustrate other exemplary embodiments of storage containers 1600 and 1700 with various matching shapes and palpable encoding. With reference to FIG. 16, container 1600, including a container base 1610 and a container lid 1660, formed of a shape and size (volume, perimeter dimensions, etc.) define it as being of a particular type. Container lid 1660, includes identifier 1665 for this particular container type encoded according to such embodiments making use of one or more raised shapes 1665 (illustrated as a raised triangle). Illustrated container lid 1660 also includes an identifier for this particular container type encoded according to such embodiments making use of Braille or other palpable indicia 1666, such as by way of example, embossed into top 1661 of lid 1660, as illustrated. In such embodiments, consistent with embodiments described above, identifier 1665 and palpable indicia 1666 matches a similar identifier and palpable indicia defined in base 1610, such as inside a bottom of base 1610, and/or in sidewall 1612 of bottom 1610, to facilitate pairing of container base 1610 with an appropriate container lid 1660.

With reference to FIG. 17, container 1700, including a container base 1710 and a container lid 1760, formed of a shape and size (volume, perimeter dimensions, etc.) define it as being of another particular type. Container bases 1710, in addition to including an identifier for this type encoded according to such embodiments making use of one or more raised shapes 1715 (illustrated as a raised square), also includes an identifier for the this particular type container encoded according to such embodiments making use of Braille or other palpable indicia 1716. In the illustrated example, identifier shape 1715 and palpable indicia 1716 are embossed into bottom 1711 of base 1710. However, the identifier and/or palpable indicia may, additionally or alternatively, be defined in sidewall 1712 of base 1710, in accordance with various alternative embodiments.

Again referring to FIG. 17, in addition to including an identifier for this particular other container type encoded according to such embodiments making use of one or more raised shapes 1765 (illustrated as a raised square) container lids 1760 may also include an identifier for this container type encoded according to such embodiments making use of Braille or other palpable indicia 1766, such as by way of example, embossed into top 1761 of lid 1760, as illustrated. In such embodiments, palpable indicia 1716 matches the palpable indicia 1766 to facilitate pairing of container base 1710 with an appropriate container lid 1760.

With respect to each of the embodiments illustrated in FIGS. 1 through 17, lids, such as 160, 260, 360, 460, 560, 660, 760, 860, 960, 1060, 1660, and 1760 are configured to engage respective bases, such as 110, 210, 310, 410, 510, 610, 710, 810, 910, 1010, 1610, and 1710 to provide selective, secure coupling of the lids to corresponding bases and prevent unintentional displacement of objects therefrom. Engagement may be provided by any of a variety of means. For example, lids 160, 260, 360, 460, 560, 660, 760, 860, 960, 1060, 1660, and 1760 and respective bases 110, 210, 310, 410, 510, 610, 710, 810, 910, 1010, 1610, and 1710 may include resilient lips, ridges or other projections configured to snap together and hold lids to corresponding bases.

In such embodiments, characters such as numbers 115/165, 215/265, 315/365, 415/465, 565, 665, 765, 865 and 915/96, letters 1015/165, or shapes 1665 and 1715/1765 may be raised or engraved such that the characters are recognizable by touch. Characters may generally be provided at any readily visible location on the container bases and container lids. For example, with reference to FIGS. 1-17, characters may be provided at bottom, internal surfaces 111, 211, 311, 411, 511, 611, 711, 811, 911, 1011, and 1711 of container bases and at top, external surfaces 161, 261, 361, 461, 561, 661, 761, 861, 961, 1061, 1661, and 1761 of container lids. In certain embodiments, this arrangement of identifiers may have the advantage of the identifier on a lid of one container indexing with the identifier in the base of another container of the same type stacked on top of the first container.

Containers may be constructed of any of a plurality of materials appropriate for the objects to be contained. Containers for smaller, lightweight objects may be made of durable but lightweight materials while containers for larger objects may be made of durable but heavier weight materials. Example materials include but are not limited to various plastics, rubber, glass, various metals and various woods.

Containers may be formed in any of a variety of sizes (volumes) and shapes to allow for storage of objects of a variety of sizes. For example, from small containers for storing screws pins, electronic components, bite size food, or the like, to large bins (e.g. 30 gallon bins, or larger) for storing bulk dry goods, clothing, or the like, including commercial containers. In some embodiments, a plurality of containers of varying size and shape may be provided as a kit. Type identifiers included with the container bases and container lids eliminate any confusion during attempts to mate lids with corresponding bases.

It should be noted that while letters, numbers and shapes have been illustrated as being used with a first encoding scheme, this scheme may include characters other than letters, numbers and shapes, such as, for example, symbols, pictures, drawings, logos, such as of National Football League, National Hockey League, National Basketball Association, Major League Baseball, National Association for Stock Car Auto Racing (NASCAR), or similar teams, images of athletes or celebrities, cartoon characters, etc., as mentioned above.

It should be noted that any or all of the encoding schemes or protocols disclosed may be used with a container system in accordance with the disclosed embodiments.

Example method 1800 of assembling containers is now described with reference to FIG. 18. With one or more objects to be contained, a user selects a first container base from among a plurality of container bases in step 1802. The user may implement any of a variety of criteria for selecting a container base including but not limited to choosing a size (volume, perimeter dimensions, etc.) and/or shape conducive to containing the objects to be contained.

Upon selecting a container base in step 1802, the user next identifies or establishes the type of the container base at 1804, by recognizing an identifier encoded on the base according to a first scheme. For example, in embodiments using schemes including color, the user may recognize the color of the container base. In a particular example, the user recognizes container base 510 as being blue at 1804. As a further example, in embodiments using schemes including alphanumeric characters, the user may recognize the alphanumeric character of the container base at 1804. In such an example, the user may recognize that container base 310 includes a “3′” or that container base 1010 includes an “A,” at 1804.

Having established the type of the selected container base in step 1804, the user next selects a container lid having an encoded identifier matching the identifier of the container base, at 1806. In embodiments using schemes including color, the user may select a first lid having the color of the selected container base. In embodiments using schemes including alphanumeric characters, the user may select a first lid having an alphanumeric character matching that of the container base. Referring to FIGS. 1-15, the character may be, for example, a number or a letter.

It should be noted that while the method described and illustrated in FIG. 18 provides for selecting a container base prior to a container lid, a user may choose to select a container lid first and subsequently choose a base corresponding with one or more encoded identifiers on the selected container lid.

Before assembling the container lid to the container base at 1810, the objects to be contained are input to the container base in step 1808. Then, finally, in step 1810, the container lid is engaged with the matching container base containing the objects. Engaging the first lid with the first container may include snapping a resilient first lid lip to a resilient first container lip. However, engagement may be accomplished by any of a variety of means conducive to providing selective and secure coupling of the lid to the base thus preventing unintentional displacement of objects therefrom.

Thereafter, in certain embodiments, containers with the same identifiers (such as containers of the same type) may be stacked, particularly wherein raised identifiers are defined in the lid and in the bottom of the base. That is, the identifier on a lid of one container may index with the identifier in the base of another container of the same type stacked on top of the first container.

FIG. 19 is a flowchart of example computer implemented storage container inventory method 1900, according to one embodiment. Storage container inventory method 1900 may be implemented in any number of computer systems, especially in an Internet-connected mode. However, storage container inventory method 1900 may be particularly well adapted for use as an application program, such as those commonly referred to as an “app,” and particularly well adapted to run on a personal computer and/or personal devices such as a smartphone, media player, personal digital assistant, wearable technology, connected glasses, tablet computing device, or the like, especially in an Internet-connected mode. Storage container inventory method 1900 may reside in memory or in storage on the computer system/device and/or may in part or whole reside on an accessible devices of storage, such as, a remote storage site, a remote server, the Internet, a computing cloud, locally on the device, and/or the like. Hence, although computer implemented storage container inventory method 1900 may be referred to below as an “app,” one will appreciate that computer implemented storage container inventory method 1900 may be implemented in any number of computer systems, in any operative manner.

Executing app 1900, a user device, such as the aforementioned computer system, personal computer, smartphone, mobile devices, media player, personal digital, assistant, connected glasses, or the like, may, at 1902, accept a user choice of a category of container to be used or being used. Such a selection may be made by the user from a drop-down menu, flick menu, or the like, displayed on the device in a Graphic User Interface (GUI) provided by app 1900.

A category of container may be selected by the user from a list that includes such categories as, food, storage, location, and/or the like. App 1900 may receive user input of an identifier or designation for the container, at 1904. This identifier may, similar to as discussed above, be practically anything that will differentiate the container. As but a few examples any identical number(s), letter(s), shape(s), picture(s), drawing(s), symbol(s), logos, such as of National Football League, National Hockey League, National Basketball Association, Major League Baseball, National Association for Stock Car Auto Racing (NASCAR), or similar teams, images of athletes or celebrities, cartoon characters, etc. A GUI screen may show a number of icons marked, for example, from one to twelve, with a number of logos, or the like, for section of one icon. Additionally, or alternatively, such identifiers may be manually input by the user in a field provided by the aforementioned GUI and/or be made by the user from a drop-down menu, flick menu, or the like, displayed in the GUI.

App 1900 may accept user input of contents of the container at 1906. User input of contents may be manually entered by the user in a field provided by the GUI and/or be selected by the user from a drop-down menu, flick menu, or the like, displayed in the GUI.

At 1908, app 1900 may generate a current date or receive a date input from the user. In various implementations, the current date may be presented to the user in the GUI, and the user may be provided an option to accept the current date. Alternatively, the user may modify and/or otherwise input the date, such as through the use of a calendar button or the like, selection of which may call a calendar or other method, such as a series of dropdown menus, or the like, for selection of a future or past date. In a similar manner to as above, the present time of day may also be accepted and/or a future or past time may be chosen, in various embodiments, as well.

App 1900 may accept user input of a location of the container at 1909 (e.g. refrigerator, freezer, garage, attic, cottage, warehouse, etc.). User input of the location may be manually entered by the user in a field provided by the GUI and/or be selected by the user from a drop-down menu, flick menu, or the like, displayed in the GUI.

At 1910, the category chosen and accepted at 1902, the identifier input received at 1904, the input contents accepted at 1906, the generated or input date (and/or time) from 1908, and the input location accepted at 1909 may be associated together. At 1912 the associated category, identifier, contents, date (and/or time), and location are stored (together). Association at 1910 may be made through use of a database (such as a relational database) to store and organize the data at 1912, may be made merely through storage of listed data (such as comma delimited data) at 1912, and/or the like, so long as the data is retrievable by app 1900. The category, identifier, input contents, generated or input date, and location may be stored to the user device, a general purpose processor based device associated with the user device, a remote storage site, a computing cloud, and/or the like. For example, the data may be stored in a cloud to make it available to the user on any number of devices, using any number of different versions of the app, in any number of locations. As a particular example, a container indexed using a mobile version of the app at a storage facility, warehouse or the like, may be reviewed at home, or at the office, using a desktop or tablet version of the application (as well as the smartphone version).

App 1900 may offer the user any number of additional, and/or alternative, options, in various implementations. For example, app 1900 may offer multiple language options, such as English, French, Spanish, etc. As but one other example option, app 1900 may allow the user to input (or select) the same identifier for at least one other container, such as through a GUI drop-down menu, flick menu, or the like, of existing indexed containers. App 1900 may then accept user input of contents of the other container(s), input in a manner similar to 1906 above (i.e. manually entered by the user in a field provided by the GUI and/or selected by the user from a drop-down menu, flick menu, or the like, displayed in the GUI). Again, app 1900 may generate a current date (and/or time) or receive a date (and/or time) input by the user, similar to 1908, above, such as through the use of a calendar button or the like, which may call a calendar or other method, such as a series of drop-down or flick menus, or the like, for selection of a future or past date (and/or time). App 1900 may again accept user input of a location of the container at 1909 through manual entered from a drop-down menu, flick menu, or the like, displayed in the GUI App 1900 also associates and stores the input contents, location and date associated with the other container(s) with the category, identifier, input contents, location and date of the original container, in accordance with such implementations. Menus and the like such as for content selection or the like in such implementations may default to correspond to the original container's selections, and/or at least a category of such contents. For example, if a first container contained “beef,” and a second container is indicated as having the same identifier, the contents selection may default to “beef,” or at least a list of foods (where “beef” may be displayed at a top of the list).

A selection to “take a picture” of the contents of the container may, in another example option, be offered to the user, such as, by way of example, as a part of acceptance of the input of contents at 1906. This selection to “take a picture” may afford the user an option capture a photograph of the contents using a camera that is a part of the user's device (such as a smartphone or media player camera). Alternatively, the picture may be a stock photograph of contents of the type input by the user, an image associated with such content (e.g. a drawing or picture of a cow, for beef) and/or may be selected through the use of a drop-down menu, flick menu, or the like, displayed in the GUI. This “picture” may be stored at 1912 along with, or referencing, the associated category, identifier, input contents, location and date. For example, in particular implementations, the user may take one or more photographs of the items placed in a large bin (clothing, important papers, shoes, sport gear, etc.) and the photographs, such as with a text description, may be stored by the app for future reference to know what is in what bin of a plurality of bins.

As another example of an option offered by implementations of app 1900, the user may be presented an interface to set at least one alert to remind the user of contents of the container, such as during the date generation or input at 1908, or elsewhere. The user may establish the reminder through the use of a calendar button or the like displayed by the GUI, selection of which may display a calendar or other method, such as a series of drop-down menus, flick menus, or the like, for selection of a date and/or time. This alert may be is in the form of a calendar reminder, a text, an email, MMS, SMS, and/or the like and app 1900 may offer the user an option in this interface to send the alert(s) to a third party in the same or different form. This third party may be selected from a contact list in the user's device, using by way of example, a GUI drop-down menu, flick menu, or the like. Thus, a user may set an “expiration date,” so-to-speak, for food stored in a container, and one or more alerts to remind the user and/or others to use the food before expiration.

Yet another implementation example of app 1900 may offer the user an option, such as in the GUI, to randomly generate a recipe for food in the container from a list of recipes. In accordance with various implementations, the user may select this option by shaking the user device, at any time app 1900 is active, or such as while viewing the contents of a container. The list of recipes may be a list of the user's recipes, and app 1900 may provide the user an interface to post recipes to a social website, or the like in the GUI.

App 1900 may provide the user a search bar, such as displayed across a top of the GUI, in various implementations, so as to receive at least part of at least one keyword input by the user. Whereupon, stored input contents, categories, identifiers, locations and/or dates may be searched for the keyword(s) and the results, for example, displayed by the GUI, for the user to browse.

As one will appreciate the present storage containers, systems and methods are particularly well suited for personal or business use. With respect to food storage a person or restaurant personal, etc. may be able to avoid spoilage, over-ordering, duplication of purchases or preparation, or the like, by employing the present storage containers, systems and methods. With respect to general storage, a person or business may organize their storage or inventory to make it more readily available, prevent loss, prevent over-ordering, prevent duplication of purchases, save time to find and analyze inventory, or the like.

While the disclosure has been presented with respect to certain specific embodiments, it will be appreciated that many modifications and changes may be made by those skilled in the art without departing from the spirit and scope of the invention. It is intended, therefore, by the appended claims to cover all such modifications and changes as fall within the true spirit and scope of the invention.

Although the above embodiments have been described in language that is specific to certain structures, elements, compositions, and methodological steps, it is to be understood that the technology defined in the appended claims is not necessarily limited to the specific structures, elements, compositions and/or steps described. Rather, the specific aspects and steps are described as forms of implementing the claimed technology. Since many embodiments of the technology can be practiced without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended. 

What is claimed is:
 1. A system for assembling containers, comprising: a first container base including an identifier for a first container type, the identifier being encoded on the first container base according to a first scheme; and a first container lid including another identifier for the first container type, the identifier being encoded on the first container base according to the first scheme.
 2. The system as set forth in claim 1, wherein the first scheme of container type encoding includes one or more characters recognizable by touch.
 3. The system as set forth in claim 1, wherein the first container base includes a type identifier provided according to a second scheme and the first container lid includes a type identifier provided according to the second scheme.
 4. The system as set forth in claim 3, wherein the second scheme includes a first color.
 5. The system as set forth in any of claim 3, wherein the first container base includes a type identifier encoded according to a third scheme and the first container lid includes a type identifier encoded according to the third scheme.
 6. The system as set forth in claim 5, wherein the third scheme includes one or more alphanumeric characters.
 7. The system as set forth in claim 1, further comprising a plurality of additional container bases including type identifiers different from the first type identifier and encoded according to first, second and third schemes; and a plurality of additional container lids including type identifiers different from the first type identifier and encoded according to the first, second and third schemes.
 8. A method of assembling containers, comprising: selecting, from among a plurality of container bases, a first container base; establishing a type of the first container base by recognizing an identifier encoded on the base according to a first scheme; selecting, from among a plurality of container lids, a first container lid having an encoded identifier matching the identifier on the container base; and engaging the first container lid with the first container base.
 9. The method as set forth in claim 8, wherein recognizing the identifier includes recognizing an alphanumeric character encoded on the container base.
 10. The method as set forth in claim 9, wherein selecting the first container lid includes selecting a first lid having the alphanumeric character of the container base.
 11. The method as set forth in claim 10, wherein recognizing the identifier includes recognizing one or more alphanumeric characters by touch.
 12. The method as set forth in claim 11, wherein selecting the first container lid includes selecting a first lid having the one or more colors.
 13. The method as set forth in claim 8, wherein recognizing the identifier includes recognizing one or more shapes.
 14. The method of claim 8, wherein engaging the first lid with the first container includes snapping a resilient first lid lip to a resilient first base lip.
 15. A user device computer implemented method comprising; accepting a user choice of a category of container; receiving user input of an identifier for the container; accepting user input of contents of the container; generating a current date or receiving a date input by the user; accepting user input of a location of the container; associating the category, identifier, input contents, generated or input date, and location; and storing the category, identifier, input contents, generated or input date, and location.
 16. The method of claim 15, further comprising: allowing the user to input the same identifier for at least one other container; accepting user input of contents of the at least one other container; generating a current date or receiving a date input by the user; accepting user input of a location of the container; associating the category, identifier, input contents, generated or input date, and location for the at least one other container ; and storing the input contents of the at least one other container, generated or input date, and location associated with the at least one other container with the category, identifier, input contents, generated or input date, and location of the container.
 17. The method of claim 15, further comprising: providing the user a search bar; receiving at least part of at least one keyword input by the user in the search bar; searching stored input contents, categories, identifiers, dates, and/or locations for the at least part of one keyword; and displaying results of the searching for the user.
 18. The method of claim 15, wherein the storing comprise storing the category, identifier, input contents, generated or input date, and location to at least one of the user device, a general purpose processor based device associated with the user device, a remote storage site, and a computing cloud.
 19. The method of claim 15, further comprising offering the user a selection to capture a photograph of the contents using the user's device and/or to select a stock photograph of contents of the type input by the user, and storing the photograph with the category, identifier, input contents, generated or input date, and location.
 20. The method of claim 15, further comprising offering the user an interface to set at least one alert to remind the user of contents of the container.
 21. The method of claim 15, further comprising offering the user an option in the interface to send at least one alert to a third party.
 22. The method of claim 21, wherein the third party is selected from a contact list in the user device.
 23. The method of claim 15, further comprising offering the user an option to randomly generate a recipe for food in the container from a list of recipes.
 24. The method of claim 23, wherein the option is selected by the user shaking the user device.
 25. The method of claim 15, further comprising providing the user an interface to post recipes to a social website, other website, a blog, or a forum. 